-
-
Notifications
You must be signed in to change notification settings - Fork 453
ref(replay): Use main thread to schedule capture #4542
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Performance metrics 🚀
|
@@ -6,7 +6,15 @@ import android.os.Looper | |||
internal class MainLooperHandler(looper: Looper = Looper.getMainLooper()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd name it (and its references) LooperHandlerWrapper
, as it's more clear that it's not just to run on the main thread, even if i think you did it just for testing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good
just a small renaming
📜 Description
A couple of replay examples with the new capture logic:
https://sentry-sdks.sentry.io/explore/replays/699aa0aff2e2496db716274d637f6a33
https://sentry-sdks.sentry.io/explore/replays/d043fb059023427b97fe54f4abf39832
💡 Motivation and Context
💚 How did you test it?
Manually
📝 Checklist
sendDefaultPII
is enabled.🔮 Next steps